Skip to main content

Your data has issues

There is a problem

  • geometry column must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Organisation Felled date Entry date Start date End date
651 16/74 EARDLEY CRESCENT

Unexpected geom type

2025-01-03
652 16/74 EARDLEY CRESCENT

Unexpected geom type

2025-01-03
653 Nov-93 EARDLEY CRESCENT

Unexpected geom type

2025-01-03
654 Nov-93 EARDLEY CRESCENT

Unexpected geom type

2025-01-03
655 36/97 EARDLEY CRESCENT

Unexpected geom type

2025-01-03
656 K31 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
657 K31 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
658 K31 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
659 K31 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
660 K31 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
661 K31 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
662 K31 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
663 18/74 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
664 18/74 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
665 18/74 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
666 18/74 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
667 18/74 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
668 Jan-92 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
669 Dec-92 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
670 Jun-94 EARLS COURT GARDENS

Unexpected geom type

2025-01-03
671 Jun-72 EARLS COURT ROAD

Unexpected geom type

2025-01-03
672 Jun-72 EARLS COURT ROAD

Unexpected geom type

2025-01-03
673 K55 EARLS COURT ROAD

Unexpected geom type

2025-01-03
674 Jun-72 EARLS COURT ROAD

Unexpected geom type

2025-01-03
675 35/96 EARLS COURT ROAD

Unexpected geom type

2025-01-03
676 K55 EARLS COURT ROAD

Unexpected geom type

2025-01-03
677 K55 EARLS COURT ROAD

Unexpected geom type

2025-01-03
678 K55 EARLS COURT ROAD

Unexpected geom type

2025-01-03
679 Jun-72 EARLS COURT ROAD

Unexpected geom type

2025-01-03
680 K32 EARLS COURT ROAD

Unexpected geom type

2025-01-03
681 17/74 EARLS COURT ROAD

Unexpected geom type

2025-01-03
682 17/74 EARLS COURT ROAD

Unexpected geom type

2025-01-03
683 17/74 EARLS COURT ROAD

Unexpected geom type

2025-01-03
684 17/74 EARLS COURT ROAD

Unexpected geom type

2025-01-03
685 K55 EARLS COURT ROAD

Unexpected geom type

2025-01-03
686 Jan-85 EARLS COURT ROAD

Unexpected geom type

2025-01-03
687 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
688 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
689 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
690 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
691 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
692 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
693 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
694 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
695 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
696 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
697 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
698 Aug-81 EARLS COURT ROAD

Unexpected geom type

2025-01-03
699 Aug-86 EARLS COURT ROAD

Unexpected geom type

2025-01-03
700 22/87 EARLS COURT ROAD

Unexpected geom type

2025-01-03

Showing rows 651 to 700 of 1000

How to fix this issue

Your dataset is missing the geometry column.

The Tree guidance explains how to fix the issue:

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL